50 simulated users executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.

260 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~34s). Sessions should end around the same time as each other for consistent behavior.

Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.

Total HTTP and supporting files (JS/CSS) latency (load time) is displayed for each session and run combination. Each vertical bar represents the amount of time a session's Shiny application had to wait before it is able to ask the server for information. A resonable amount of time to wait as been set to 5s. Warmup and cooldown sessions are displayed outside the dotted maintenance period lines.

Maximum WebSocket latency (calculation time) is displayed for each session and run combination. The maximum time is shown to convey the longest amount of time a user would have to wait for a response from the Shiny server. Warmup and cooldown sessions are displayed outside the dotted maintenance period lines.

Event plots are arranged by the slowest maximum time within each plot.

slowest maximum times

Event plots are arranged by the slowest minimum time within each plot.

slowest minimum times

Label Max time Min time
Event 35) Updated: cpuPlot 0.202 0.008
Event 9) Updated: cpuPlot 0.195 0.008
Event 25) Updated: cpuPlot 0.193 0.008
Event 27) Updated: cpuPlot 0.191 0.008
Event 5) Updated: cpuPlot 0.180 0.013
Event 4) Initialize Session 0.151 0.000
Event 23) Updated: cpuPlot 0.135 0.008
Event 19) Updated: cpuPlot 0.125 0.008
Event 1) Get: Homepage 0.108 0.023
Event 17) Updated: cpuPlot 0.107 0.007
Event 7) Updated: cpuPlot 0.102 0.007
Event 2) Start Session 0.082 0.003
Event 29) Updated: cpuPlot 0.079 0.007
Event 15) Updated: cpuPlot 0.078 0.007
Event 11) Updated: cpuPlot 0.078 0.007
Event 13) Updated: cpuPlot 0.074 0.009
Event 31) Updated: cpuPlot 0.071 0.008
Event 21) Updated: cpuPlot 0.065 0.008
Event 33) Updated: cpuPlot 0.062 0.008

Event plots are arranged by the largest slope magnitude found when fitting a line to each run.

largest slope magnitudes

Event plots are arranged by the largest intercept magnitude found when fitting a line to each run

largest intercept magnitudes

Event plots are arranged by the largest error magnitude found when fitting a line to each run.

largest error magnitudes

Label Slope Intercept Error
Event 1) Get: Homepage -0.029 1.461 0.065
Event 21) Updated: cpuPlot -0.016 0.830 0.043
Event 29) Updated: cpuPlot -0.015 0.794 0.059
Event 31) Updated: cpuPlot -0.015 0.782 0.051
Event 15) Updated: cpuPlot -0.014 0.734 0.058
Event 23) Updated: cpuPlot -0.013 0.679 0.115
Event 27) Updated: cpuPlot -0.012 0.606 0.169
Event 13) Updated: cpuPlot -0.011 0.594 0.051
Event 9) Updated: cpuPlot -0.011 0.558 0.173
Event 33) Updated: cpuPlot -0.010 0.534 0.038
Event 11) Updated: cpuPlot -0.010 0.525 0.055
Event 5) Updated: cpuPlot -0.010 0.525 0.152
Event 2) Start Session -0.008 0.421 0.066
Event 35) Updated: cpuPlot -0.007 0.367 0.179
Event 7) Updated: cpuPlot -0.005 0.284 0.084
Event 19) Updated: cpuPlot -0.005 0.275 0.102
Event 17) Updated: cpuPlot -0.004 0.228 0.085
Event 25) Updated: cpuPlot 0.003 -0.138 0.169
Event 4) Initialize Session -0.003 0.149 0.143